Emergency Locator System

ABSTRACT

Systems and methods for providing distributed notification of an emergency event are disclosed. A system according to the invention can include a remote device that is communicatively coupled to a base station. The remote device can include an activation device, a GPS signal receiver, a remote device controller, and a location signal transmitter. The GPS signal receiver is adapted to receive global positioning signals from each of a plurality of global positioning satellites. The transmitter is adapted to transmit location signals to the base station. The base station can include a contact profile data store, a location signal receiver, a base station controller, and a notification signal transmitter. The location signal receiver is adapted to receive location signals from the remote device. The notification signal transmitter is adapted to transmit notification signals to each of a plurality of contacts, which can include an emergency service.

This application is a continuation of co-pending U.S. patent applicationSer. No. 09/965,984 (BE1-0083US), filed Sep. 28, 2001, which isincorporated herein by reference.

FIELD OF THE INVENTION

This invention relates to the field of telecommunications. Moreparticularly, the invention relates to systems and methods forconcurrent notification of a user-provided list of emergency contacts.

BACKGROUND OF THE INVENTION

Unfortunately, individuals sometimes find themselves in situations inwhich they need assistance. For example, an individual might suffer asudden heart attack, or an unexpected traffic problem, such as a vehiclebreakdown or accident, or there might be an intruder in the house, orsomeone suspicious approaching, or the like. In such situations, theindividual could call a predefined emergency telephone number, such as911, to notify authorities and request such emergency services aspolice, ambulance, fire, towing, or the like. Alternatively oradditionally, the individual could call one or more family members,friends, or other contacts to notify them of the situation as well.

In an emergency, however, individuals typically cannot afford the timeto make a number of phone calls to notify various others that thesituation exists. For example, if an individual is having a heartattack, he would not likely want to make more than one phone call, norwould he likely be able to do so. If an intruder were in the house, theindividual would want to focus on getting out of the house, rather thanmaking a number of calls.

There are also emergency situations in which the individual cannotactually dial a phone. For example, if the individual has suffered aheart attack, he might not be able to dial the number, or be lucidenough, while in pain, even to remember the number to dial. Similarly,if the individual is being robbed at gunpoint, the robber is unlikely toallow the victim to make a phone call. If an intruder were in the houseor a suspicious person approaching, the individual would likely not wantto be heard while calling for help.

Hence, there is a need in the art for systems and methods by which anindividual in need of emergency assistance can notify a plurality ofcontacts by initiating a single communication. There is especially aneed for such systems and methods wherein such notification can betriggered without requiring the individual to dial a phone or to speak.

BRIEF SUMMARY OF THE INVENTION

The invention satisfies the aforementioned needs in the art by providingsystems and methods for providing distributed notification. Theinvention allows people in an emergency situation to providenotification and location information of an emergency event. People whoare in danger can activate a device, which can trigger a notification tothe appropriate emergency service for that area, as well as to thetelephone numbers, pager numbers, email addresses, etc., of a predefinedlist of emergency contacts.

An emergency services operator, such as a 911 operator, for example, whoreceives the notification signal can quickly pinpoint the location ofthe person in trouble by using location information contained in thesignal provided by the device. Preferably, the device includes a GlobalPositioning System (GPS) receiver for this purpose. The list ofemergency contacts would receive a message (such as a voice or textmessage, for example), which would provide access to more informationregarding the emergency (such as status and location, for example).Voice portal technology could be used to provide additional, up-to-dateinformation about the emergency. This service can be activated using aspecial beeper, car-mounted device, or jewelry-type transceiver devicethat contains an emergency activation button.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

Other features of the invention are further apparent from the followingdetailed description of the embodiments of the present invention takenin conjunction with the accompanying drawing, of which:

FIG. 1 is a block diagram of an exemplary telecommunications network inwhich the principles of the invention can be employed;

FIG. 2 is a block diagram of a preferred embodiment of an emergencylocator system according to the invention;

FIG. 3 depicts exemplary contents of a contact profile data storeaccording to the invention; and

FIGS. 4A and 4B provide a flowchart of a preferred embodiment of amethod according to the invention for concurrent notification of apredefined list of emergency contacts.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to the figures, an embodiment of the systems and methodsof the invention will be described. Basic telephony concepts andterminology are used throughout the description as would be understoodby one of skill in the art.

FIG. 1 is a block diagram of an exemplary telecommunication network 100,such as a public switched telecommunications network (PSTN), in whichthe principles of the invention can be employed. More particularly, FIG.1 illustrates a simplified advanced intelligent network (AIN). AINsystems are described in U.S. Pat. No. 5,701,301, the disclosure ofwhich is hereby incorporated herein by reference. Though the variousfeatures and aspects of the invention can be utilized in conjunctionwith an AIN, it should be understood that the invention is not limitedto AIN-based systems, and that other networks and system arrangementscan be used in accordance with the invention.

As shown, the AIN 100 can include a plurality of service switchingpoints (SSPs) 114, 116. SSPs 114, 116 are capable of generating AINqueries. An SSP, which is also known as a “central office,” is basicallya switch and the terms are used interchangeably herein. SSPs 114 and 116can comprise, for example, DMS100 or 5ESS switches. These switches canbe manufactured by, for example, Lucent Technologies, Inc. or NortelNetworks.

Each of the SSPs 114, 116 can have one or more subscriber lines 111connected thereto. Subscriber lines 111 may also be referred to ascalling lines. Each SSP 114, 116 serves a designated group of callinglines 111, and thus, the SSP that serves a particular calling line maybe referred to as its serving switch. Typically, each calling line 111is connected to one or more pieces of terminating equipment 110, 112,such as a telephones, facsimile machines, computers, modems, or othersuch telecommunication devices.

SSPs 114, 116 are interconnected by one or more trunk circuits 115.Trunks 115 are basically the voice paths via which communications areconnected between SSPs. The term “communication” or “call” is usedherein to include all messages that may be exchanged between the callingparty and the called party in a telecommunication network, such asillustrated in FIG. 1. Trunk 115 can be either a Signaling System 7(SS7) controlled multi-frequency (MF) trunk, or primary rate interface(PRI) trunk or the like. The type of trunk will be in accordance withboth the sending and receiving SSP to which it is connected.

Each SSP 114, 116 can include different types of facilities and/ortriggers. SSPs 114 and 116 are programmable switches that can performsome or all of the following functions: recognize AIN-type calls, launchqueries, and receive commands and data to further process and routeAIN-type calls. When one of SSPs 114 or 116 is triggered by an AIN-typecall, the triggered SSP 114 or 116 formulates and sends an AIN query.Based on the reply from the AIN network, SSP 114 or 116 responds to callprocessing instructions received.

Each of SSPs 114 and 116 is connected to a signal transfer point (STP)117 via respective data links 150, 152. Data links 150, 152 can employSS7, for example, though it should be understood that any suitablesignaling protocol could be employed. To facilitate signaling and datamessaging, each SSP 114 and 116 can be equipped with Common ChannelSignaling (CCS) capabilities, e.g., SS7, which provides two-waycommunications of data messages over CCS links 150 and 152 betweencomponents of the AIN network. The data messages can be formatted inaccordance with the Transaction Capabilities Applications Part (TCAP).Alternatively, Integrated Service Digital Network (ISDN) Users Part(ISUP) can be used for signaling purposes between, for example, SSPs 114and 116. In such a case, SSPs 114 and 116 can be equipped with thecapability to map appropriate data between TCAP and ISUP protocols, andvice versa. The telephone network basically employs an upper-levelsoftware controlled network through the STPs and the SCP.

SSPs 114 and 116 may allow normal switch processing to be suspended atspecific points in a call so that the switch can send an AIN messagequery via signaling transfer point (STP) 117 to SCP 118, 119 or 120. SCP118, 119 or 120 may execute software based service logic and returncall-processing instructions to the triggering AIN SSP. New services maybe provisioned by assigning AIN SSP triggers to customer lines, trunks,and/or NANP (North American Numbering Plan) telephone numbers.

Much of the intelligence of the AIN resides in a type of AIN elementreferred to as a service control point (SCP) 118, 119, 120 that isconnected to STP 117 over an SS 7 data link, or the like, 154, 156 or158. Accordingly, the connections by links 150, 152, 154, 156, and 158are for signaling purposes and allow SSPs 114 and 116 to send messagesto, and receive messages from, SCP 118, 119 and 120.

Among the functions performed by SCP 118, 119, 120 is the hosting ofnetwork databases and subscriber databases, which may be stored inrespective data storage objects 123, 124, 125. For example, data storageobject 123 is shown as a database communicatively coupled to SCP 118,although data storage object 123 can be embodied as a component withinSCP 118, such as an internally-mounted hard disk device. The databasesstored in data storage object 123 may be used in providingtelecommunications services to a customer. Typically, SCP 118, 119, 120is also the repository of service package applications (SPAs) that areused in the application of telecommunication services, enhancedfeatures, or subscriber services to calling lines. Additionally, SPAsmay use databases for providing telecommunication services.

A set of triggers can be defined at the SSPs 114, 116. A trigger in theAIN is an event associated with a particular call that initiates a queryto be sent to SCP 118, 119, or 120. The trigger causes selected SCP 118,119, or 120 to access, if necessary, its respective database 123, 124,or 125 for processing instructions with respect to the particular call.The results of the SCP processing and/or database inquiry is/are sentback to selected SSP 114 or 116 in a response through STP 117. Thereturn packet includes instructions to SSP 114, 116 as to how to processthe call. The instructions may be to take some special action as aresult of a customized calling service, enhanced feature, or subscriberservice. In response, switch 114, 116 moves through its call states,collects the called digits, and generates further packets that are usedto set up and route calls. Similar devices for routing calls amongvarious local exchange carriers are provided by regional STP andregional SCP.

An example of such a trigger is a termination attempt trigger (TAT),which causes a query to be sent to SCP 118, 119, or 120 whenever anattempt is made to terminate a call on the line of subscriber 110 or112. Another type of trigger that may be used is a Public Office DialingPlan (PODP) trigger, though it should be understood that the principlesof the invention include the use of other triggers.

The AIN can also include a services circuit node 134 (SCN), which mayalso be referred to herein as a services node (SN). SN 134 is aninteractive data system that acts as a switch to transfer calls. SN 134may provide interactive help, collect voice information fromparticipants in a call, and/or provide notification functions. SN 134can be a Lucent Technologies Star Server FT Model 3200 or Model 3300although other such devices can be employed. SN 134 can include voiceand dual tone multi-frequency (DTMF) signal recognition devices and/orvoice synthesis devices. In addition, SN 134 can include a data assemblyinterface. SN 134 can be connected to local SCP 118, 119, 120 viarespective data links 166, 168, 170 using an X.25, SS 7 or TCP/IPprotocol or any other suitable protocol. In addition, SN 134 typicallymay be connected to one or more (but usually only a few) SSPs viaIntegrated Service Digital Network (ISDN) lines or any other kind ofsuitable telephone lines 132.

One skilled in the art will further recognize that the above-describednetwork is a simplified network meant for explanatory purposes. It islikely that a telephone network might include numerous user stations,SSPs, STPs, SCPs, and SNs along with other telephone network elements,and can employ other types of triggers without departing from the spiritand scope of the invention.

FIG. 2 is a block diagram of a preferred embodiment of a systemaccording to the invention for providing distributed notification. Asshown, a system according to the invention can include a remote device200, which is preferably a small, hand-held device, having a form factorof a pager, for example. The remote device 200 is communicativelycoupled to a base station 210 via a communications link 209. Preferably,the communications link 209 is a wireless, radio-frequency (RF)communications link.

The remote device 200 can include an activation device 202, a GPS signalreceiver 204, a remote device controller 206, and a location signaltransmitter 208. The GPS signal receiver 204 is adapted to receiveglobal positioning signals from each of a plurality of globalpositioning satellites 15 via respective GPS links 20. Preferably, theGPS signal receiver 204 includes a GPS antenna (not shown) for receivingthe global positioning signals from the GPS satellites. The transmitter208 is adapted to transmit location signals via a communication link 209to a base station 210.

The activation device 202 is electrically connected to the remote devicecontroller 206. The activation device 202 can be a button that sends anelectrical impulse to the remote device controller 206 when the buttonis pushed. Preferably, to reduce the incidence of accidental triggering(and, consequently, the incidence of false alarms), the button can bedepressed into a housing of the remote device, covered with a cap, orotherwise disposed so as to minimize inadvertent activation of thedevice.

Alternatively, the activation device 202 can be coupled to another eventtrigger, such as a collision sensor in an automobile, for example, suchas would be used to detect a collision for purposes of airbagdeployment. When the collision sensor detects that the automobile hasbeen involved in a collision, the collision sensor transmits a signal,such as an electrical impulse, to the activation sensor 202, which, inturn, transmits an electrical impulse to the remote device controller206. Alternatively, the collision sensor and the activation sensor 202can be one in the same. That is, the collision sensor can beelectrically connected directly to the remote device controller 206 andtransmit an electrical signal to the remote device controller 206 upondetection that the automobile has been involved in a collision. In suchan embodiment, the device can be integrated into an automobile.

Preferably, the remote device controller 206 includes a microprocessorthat contains computer executable instructions for controlling theoperation of the remote device 200 and for performing a method accordingto the invention as will be described in detail below. Preferably, theremote device 210 includes a memory 207 for storing a remote deviceidentifier, such as a serial number, that uniquely identifies the remotedevice 200. The remote device can also include a power supply (notshown), such as a watch battery, and a clocking source (not shown).

The base station 210 can include a contact profile data store 212, alocation signal receiver 214, a base station controller 216, and anotification signal transmitter 218. The location signal receiver 214 isadapted to receive location signals via the communications link 209 fromthe remote device 200. The notification signal transmitter 218 isadapted to transmit notification signals to each of a plurality ofcontacts 220-1, 220-2, . . . , 220-N via respective communication links219-1, 219-2, . . . , 219-N. Preferably, the notification signaltransmitter 218 is further adapted to transmit notification signals toan emergency service 222 via a corresponding communications link 221.Generally, the emergency service can be thought of as an additional(N+1^(St)) contact.

Preferably, the base station controller 216 includes a microprocessorthat contains computer executable instructions for controlling theoperation of the base station 210 and for performing a method accordingto the invention as will be described in detail below. Preferably, thebase station 210 includes a memory 217 for storing voice and textnotification templates as will be described in detail below.

FIG. 3 depicts exemplary contents 300 of a contact profile data store inaccordance with the invention. As shown, the contact profile data storecan contain a plurality of entries or contact profiles 302. Each contactprofile 302 is associated with a remote device identifier 304 such asdescribed above in connection with FIG. 2. Each remote device identifieris associated with a respective subscriber identifier 306 and contactlist 308. The subscriber identifier 306 can include the name of theperson who is registered as the owner of the remote device, or any otherdata that can be used to associate the remote device with a person. Eachcontact list 308 includes one or more contacts. Each contact isassociated with a respective contact address 310 and contact type 312.

The contact address 310 is an address at which the contact is to benotified, i.e., an address to which the base station should send anotification signal at the occurrence of a triggering event. Examples ofcontact addresses 310 include telephone numbers, pager numbers, faxnumbers, or email addresses.

The contact type 312 represents the type of notification that should beprovided to the contact at the occurrence of a triggering event.Examples of contact types 312 include voice or text. Preferably, thebase station provides voice notification signals to the contact wherethe contact address is a telephone number, and text notification signalswhere the contact address is a pager number, fax number, or emailaddress.

Preferably, the subscriber provides the data for the associated contactprofile 302. Preferably, the subscriber can setup the contacts listinitially via a Web site provided by the provider of the emergencylocator service. The subscriber logs on to the Web site using hissubscriber ID and a prearranged password. The password can be setinitially by the provider of the emergency locator service, with anoption for the subscriber to change the password if he so desires.

The subscriber can then provide the list of contacts and a contactaddress for each contact in the list. The server on which the Web siteresides (the Web server) can provide the subscriber with options toindicate whether the address corresponds to a telephone, pager, faxmachine, email address or the like. In this way, the server candetermine whether the contact type is voice or text. Similarly, thesubscriber can add, delete, or modify data in the subscriber's entry inthe contact profile data store. Preferably, the Web server is coupled tothe base station such that the Web server can update the contact profiledata store to reflect the subscriber's input. Alternatively, the basestation can be implemented on a server that provides the Web site, orother user interface that the subscriber can access remotely by computeror telephone, for example.

Preferably, the server tests and validates the contact addresses thatthe subscriber provides to ensure that the contact addresses are valid,working addresses. For example, if the subscriber provides an emailaddress, the server can send a test email message to the address. If themessage is not returned as undeliverable, then the server determinesthat the email address is a valid address, and stores the address in thesubscriber's contacts list. Similarly, if the subscriber provides atelephone number, fax number, pager number, or the like, the server caninitiate a test call to the number provided to determine whether thenumber is valid and active. If so, the server updates the contacts listto include the subscriber-provided contact address.

FIGS. 4A and 4B provide a flowchart of a method 400 according to theinvention for providing distributed notification. At step 402, theremote device receives global positioning signals from a plurality ofGPS satellites. As described above in connection with FIG. 2, the remotedevice can include a GPS receiver that is adapted to receive the globalpositioning signals. The remote device can receive GPS signalscontinuously or, more preferably, to reduce power consumption, theremote device receives signals only after a triggering event has beendetected. In such an embodiment, the remote device controller initiates(“turns on”) the GPS receiver or otherwise causes the GPS receiver toreceive the GPS signals upon detection of the occurrence of a triggeringevent. The GPS receiver passes the received GPS signals to the remotedevice controller.

At step 404, the remote device detects the occurrence of a triggeringevent. In an embodiment wherein the remote device includes an activationbutton, a triggering event occurs when the activation button is pushed.In such an embodiment, the remote device controller detects theelectrical impulse from the button and thereby recognizes that atriggering event has occurred. In an alternate embodiment wherein theactivation sensor is coupled to an automobile's collision sensor, forexample, a triggering event occurs when the collision sensor detectsthat the automobile has been involved in an accident. In such anembodiment, the remote device controller detects the electrical signalfrom the collision sensor (via the activation sensor if the activationsensor is separate form the collision sensor) and thereby recognizesthat a triggering event has occurred.

Upon detection of the occurrence of a triggering event at step 404, theremote device, at step 406, transmits a location signal to the basestation. The remote device controller forms a location signal datapacket, and passes the location signal data packet to the transmitter.The remote device transmitter transmits the location signal data packetas a location signal to the base station. Preferably, the locationsignal includes the remote device identifier, which the remote devicecontroller retrieves from the memory in the remote device, and arepresentation of the location of the remote device. To reduce theprocessing requirements of the remote device, the location signalpreferably contains the raw GPS data that is downloaded from the GPSsatellites. Alternatively, the location signal can contain a longitudeand latitude of the remote device. In such an embodiment, the remotedevice controller is programmed to compute the longitude and latitudefrom the raw GPS data.

At step 408, the base station receives the location signal via the basestation receiver. The base station receiver passes the location signaldata packet to the base station controller, which extracts the remotedevice identifier from the location signal data packet. At step 410, thebase station controller determines whether the remote device belongs toa subscriber to the emergency locator service. That is, the base stationcontroller determines whether the remote device identifier extractedfrom the location signal corresponds to a remote device identifier inthe contact profile data store. The remote device identifier might notbe in the contact profile data store because the subscriber'ssubscription to the emergency location service might not have beenactivated or might have lapsed, for example.

If, at step 410, the base station controller determines that the remotedevice identifier extracted from the location signal does not correspondto a remote device in the contact profile data store, then, at step 412,the base station controller performs non-subscriber processing.Non-subscriber processing can be, for example, ignoring the call, ornotifying an emergency service that an emergency has been detected atthe location of the remote device, even though the identity of thesubscriber cannot be provided to the emergency service, nor can anyadditional contacts be notified.

If, at step 410, the base station controller determines that the remotedevice identifier extracted from the location signal does correspond toa remote device in the contact profile data store, then, at step 414,the base station controller determines the corresponding subscriber ID.Preferably, the base station controller retrieves the subscriber ID fromthe contact profile associated with the remote device ID. Alternatively,the base station controller can extract the subscriber ID from thelocation signal. In such an embodiment, the remote device stores thesubscriber ID in memory. The remote device controller retrieves thesubscriber ID from memory and includes the subscriber ID in the locationsignal.

At step 416, the base station controller determines the location of theremote device (and, consequently, of the subscriber in the emergencysituation). Preferably, where the location signal includes raw globalpositioning data, the base station controller computes a longitude andlatitude from the raw global positioning data usingwell-known-techniques. Thus, the base station controller computes alongitude and latitude that correspond to the location of the remotedevice. Alternatively, the remote device controller can compute thelongitude and latitude of the remote device from the raw GPS data, andprovide the longitude and latitude to the base station in the locationsignal.

Preferably, the base station converts the raw GPS data (or the longitudeand latitude) into a street address. The base station can include a datastore that contains a mapping of longitude/latitude into street address.Alternatively, the base station can access such a data store via anetwork, such as the Internet. Alternatively, the base station canaccess a remote processor via such a network, provide thelongitude/latitude data to the remote processor, and receive acorresponding street address from the remote processor.

At step 417, the base station controller retrieves from the contactprofile data store the contact data associated with the remote deviceidentifier. For each of the contacts in the contact list, the basestation controller determines whether the contact type is voice or text.If, at step 418, the base station controller determines that the contacttype is voice, then, at step 420, the base station controller retrievesa voice notification template from memory. At step 422, the base stationcontroller modifies the voice notification template with event specificdata to form a voice notification file.

For example, a voice notification template can be an audio or text filethat corresponds to the message “An emergency involving [subscriber ID]has been reported at [location of remote device]. Emergency services[have/have not] been contacted. Please contact us for more information.”At the occurrence of a triggering event, the base station controller canmodify the voice notification template by interleaving audio or textcorresponding to the subscriber ID and location into the voicenotification template to form the voice notification file. Depending onwhether the contacts list includes an emergency service, the voicenotification file is modified accordingly. If either or both of thevoice notification template and voice notification file are to be storedas audio, then existing text-to-speech technology can be employed toconvert text to audio before it is stored.

At step 424, the base station controller provides a voice notificationsignal to the contact address via the base station transmitter. Forexample, where the contact address is a telephone number, the basestation controller initiates a telephone call to the contact address. Inan embodiment wherein the base station is implemented within a servicenode, the communications link between the base station and a contacthaving a telephone number as a contact address can include one or moreSSPs, trunks, calling lines, and the like as described in FIG. 1. If thevoice notification file is stored as an audio file, then the basestation controller causes the audio file to be played over thecommunications link to the contact when the base station controllerdetects that the call has been answered. If the voice notification fileis stored as text, then text-to-speech technology is employed to convertthe text file into audio, which is then played over the communicationslink to the contact.

If, at step 426, the base station controller determines that the contacttype is text, then, at step 428, the base station controller retrieves atext notification template from memory. At step 430, the base stationcontroller modifies the text notification template with event specificdata to form a text notification file.

For example, a text notification template can be a text file thatcorresponds to the message “An emergency involving [subscriber ID] hasbeen reported at [location of remote device]. Emergency services[have/have not] been contacted. Please contact us for more information.”At the occurrence of a triggering event, the base station controller canmodify the text notification template by interleaving text correspondingto the subscriber ID and location into the text notification template toform the text notification file. Depending on whether the contacts listincludes an emergency service, the text notification file is modifiedaccordingly.

At step 432, the base station controller provides a text notificationsignal to the contact address via the base station transmitter. Forexample, where the contact address is a pager number, the base stationcontroller initiates a call to the contact address. When the controllerdetects that the call has been answered, the controller provides thetext notification to the contact's pager. Similarly, where the contactaddress is a fax number, the base station controller initiates a call tothe contact address and, when the controller detects that the call hasbeen answered, the controller provides the text notification to thecontact's fax machine. In an embodiment wherein the base station isimplemented within a service node, the communications link between thebase station and a contact having a pager number or fax number as acontact address can include one or more SSPs, trunks, calling lines, andthe like as described in FIG. 1.

Where the contact address is an email address, the base stationcontroller sends to the contact address, via a network such as theInternet, an email that includes the text notification. Thecommunications link between the base station and a contact having anemail address as a contact address can be part of a wide area network,such as the Internet, for example. Accordingly, the base station caninclude a network access program, such as a Web browser, for example,that enables the base station to connect to the network.

The process continues at step 417 until all the contacts in the listhave been notified.

It is anticipated that a subscriber might inadvertently activate aremote device, thereby causing a false alarm to be sent to the contactson that subscriber's contacts list. This might occur, for example, wherethe subscriber accidentally pushes the activation button on the remotedevice. Another example of a false alarm can occur where a subscriber atfirst perceives a situation as an emergency, but later determines thatthe situation is harmless. Sometimes, even when the emergency situationis real, the situation is resolved within a short period of time. Forexample, the parties to a minor traffic accident might agree that anydamage is minimal, and that they will go their separate ways. In such asituation, the subscriber might wish to rescind the call to theemergency contacts. At other times, the nature of the emergency mightrequire that the subscriber be moved from the location, such as when thevictim of an automobile accident needs to be taken to a hospital. Ineach of these examples, and in others, the contacts could arrive at thelocation of the emergency event only to find that the subscriber is notin danger or is no longer there.

To reduce the incidence of false alarms and the likelihood that acontact will arrive at a location after the situation has been resolvedor the subscriber has already left, a system according to the inventioncan provide up-to-date information about the location of the remotedevice or the status of the emergency situation. Rather than treatingthe emergency as an isolated event that occurs when the remote device isactivated, to provide up-to-date information, the emergency locatorsystem can treat the emergency as an ongoing situation that begins whenthe remote device is activated. The system considers the emergencysituation to be “ongoing” from the time the remote device is activated,until either the subscriber “terminates” the event, or a predefinedtimeout period expires.

While the situation is ongoing, the remote device can continually orperiodically send location information to the base station.Alternatively, the base station can periodically interrogate the remotedevice by sending a location request signal to the remote device fromtime to time. In response to receiving the location request signal, theremote device can provide the base station with its current location. Ina manner as described above, the base station can maintain the currentlocation of the remote device (which, presumably, is the currentlocation of the subscriber).

Preferably, the system provides emergency contacts with access tocurrent location information via a network connection, such as by usinga telephone or Internet appliance. That is, the contact can retrieveup-to-date information from the base station server by establishing anInternet connection to a Web site that the provider offers.Alternatively, where voice portal technology is available for mappinginformation provided on a Web site into intelligible speech, theemergency contact can retrieve the location information from the website by telephone. In still another embodiment, the emergency contactcan place a call to a live operator who retrieves the currentinformation from the server and relays it to the contact. The providerof the emergency locator service can provide the contacts with anaddress, such as a web site address or telephone number, via thenotification signal.

To maintain security in such a system, the emergency contact ispreferably required to provide contact identification information, suchas the contact id and a prearranged password. Preferably, the subscriberprovides the contact id at the time the subscriber sets up the contactslist. The system can provide an initial password for each contact, andthe contact can change the password during subsequent use of the system.

When the situation has been resolved, or if the alarm was false, thesubscriber can contact the emergency locator service (by telephone,email, or a website, for example), to notify the service that thesituation is “over.” If the subscriber does not make such a contactwithin a predefined timeout period, the system treats the situation asif it is over. That is, in either event, the system no longer tracks thelocation of the remote device, and, therefore, no longer providesupdated location information to the emergency contacts. Preferably, thetimeout period is defined to be long enough to accommodate mostemergency situations (e.g., one hour).

The emergency service or the subscriber can also provide updated statusinformation to the system so that other emergency contacts can retrieveup-to-date status. For example, in the case of a minor traffic accident,the emergency service or subscriber could contact the emergency locatorservice to advise that everyone at the scene is uninjured. On the otherhand, if the accident were severe, the emergency service (or thesubscriber, if able) could notify the emergency locator service thatindividuals have been injured and taken (or will be taken) to a specifichospital for example. The emergency contacts can then retrieve thisupdated status information in the same manner as described above inconnection with retrieval of updated location information.

Thus, there have been described systems and methods for providingdistributed notification. Those skilled in the art will appreciate thatnumerous changes and modifications can be made to the preferredembodiments of the invention, and that such changes and modificationscan be made without departing from the spirit of the invention. It isintended, therefore, that the appended claims cover all such equivalentvariations as fall within the true spirit and scope of the invention.

1. One or more computer-readable media having computer-executableinstructions for: testing contact data associated with a plurality ofcontacts, to validate that the contact data for each is valid, thetesting comprising initiating a test call to each of the contacts;processing an emergency notification message from a remote device,wherein the emergency notification message comprises a location signalthat represents a current location of a remote device; determining froma contact profile data store a plurality of contacts for notification ofthe emergency notification, wherein the contact profile data storecontains a contact profile that is associated with the remote device andincludes respective contact data relating to each of the plurality ofcontacts; and communicating information pertaining to the emergencynotification to each of the plurality of contacts and to an emergencyservice; and obtaining an updated notification message from the remotedevice, wherein the updated notification message reflects a currentlocation of the device.
 2. The one or more computer-readable media ofclaim 1, wherein the emergency notification message further comprisesevent status information about the emergency, and wherein the updatednotification message further comprises up-to-date event statusinformation.
 3. The one or more computer-readable media of claim 2,wherein the event status information comprises one of (i) an indicationthat everyone at the location is uninjured, and (ii) an indication thatindividuals at the location have been injured.
 4. The one or morecomputer-readable media of claim 3, wherein when the event statusinformation an indication that individuals at the location have beeninjured, the status further including an indication of a hospital towhich the injured individuals have been or will be taken.
 5. The one ormore computer-readable media of claim 1, wherein the contact profiledata store further contains a subscriber identifier associated with theremote device.
 6. The one or more computer-readable media of claim 1,wherein the contact profile data store further contain a respectivecontact address and contact type associated with each of the pluralityof contacts.
 7. The one or more computer-readable media of claim 1,having further computer-executable instructions for providing theupdated notification message to each of the plurality of contacts and tothe emergency service until a deactivation event occurs.
 8. The one ormore computer-readable media of claim 7, wherein the deactivation eventis an expiration of a predefined timeout period.
 9. The one or morecomputer-readable media of claim 7, wherein the deactivation event is atermination by a user of the remote device.
 10. The one or morecomputer-readable media of claim 1, further includingcomputer-executable instructions for providing a website by which theplurality of contacts can retrieve location information via a networkconnection.
 11. A method for providing distributed notification, themethod comprising: processing an emergency notification message from aremote device, wherein the emergency notification message comprises alocation signal that represents a current location of a remote device;determining from a contact profile data store a plurality of contactsfor notification of the emergency notification, wherein the contactprofile data store contains a contact profile that is associated withthe remote device and includes respective contact data relating to eachof the plurality of contacts; and communicating information pertainingto the emergency notification to each of the plurality of contacts andto an emergency service; and obtaining an updated notification messagefrom the remote device, wherein the updated notification messagereflects a current location of the device.
 12. The method of claim 11,wherein the emergency notification message further comprises eventstatus information about the emergency, and wherein the updatednotification message further comprises up-to-date event statusinformation.
 13. The method of claim 12, wherein the event statusinformation comprises one of (i) an indication that everyone at thelocation is uninjured, and (ii) an indication that individuals at thelocation have been injured.
 14. The method of claim 13, wherein when theevent status information an indication that individuals at the locationhave been injured, the status further including an indication of ahospital to which the injured individuals have been or will be taken.15. The method of claim 12, further comprising providing the updatednotification message to each of the plurality of contacts and to theemergency service until a deactivation event occurs.
 16. The method ofclaim 11, further comprising providing a website by which the pluralityof contacts can retrieve location information via a network connection.17. The method of claim 11, further comprising determining the identityof the subscriber associated with the remote device from the contactprofile.
 18. A system for providing emergency notification, the systemcomprising: a signal receiver at a base station for receiving locationsignals that represent a current location of a receiver; a contactprofile data store that contains a contact profile that is associatedwith a remote device identifier and includes respective contact datarelating to each of a plurality of contacts; and a signal transmitter atthe base station that (i) provides to each of the plurality of contactsand to an emergency service a respective notification message thatcontains a location of a remote device associated with the remote deviceidentifier; (ii) obtains an updated notification message from the remotedevice, wherein the updated notification message reflects a currentlocation of the device; (iii) and provides the updated notificationmessage to each of the plurality of contacts and to the emergencyservice until a deactivation event occurs.
 19. The system of claim 18,wherein the updated notification message is obtained by one of (i)sending an updated location signal at the base station from the remotedevice and (ii) sending a location request signal to the remote devicefrom the base station.
 20. The system of claim 18, wherein thedeactivation event comprises an expiration of a predefined timeoutperiod or a termination by the subscriber.